| Package | hl7.ehrs.uv.phrsfmr2 |
| Type | Requirements |
| Id | Id |
| FHIR Version | R5 |
| Source | http://hl7.org/ehrs/uv/phrsfmr2/https://build.fhir.org/ig/HL7/phrsfm-ig/Requirements-PHRSFMR2-PH.2.5.7.html |
| Url | http://hl7.org/ehrs/uv/phrsfmr2/Requirements/PHRSFMR2-PH.2.5.7 |
| Version | 2.0.1-ballot |
| Status | active |
| Date | 2025-04-03T15:15:30+00:00 |
| Name | PH_2_5_7_Manage_Surgical_History |
| Title | PH.2.5.7 Manage Surgical History (Function) |
| Experimental | False |
| Authority | hl7 |
| Description | Manage the PHR Account Holder's history of surgical procedures. |
| Purpose | The list of past procedures is a useful summary of what has been done in the past and anatomic changes have occurred that might influence current assessments and treatments. It is important to capture any surgical implants and associated lot/serial numbers for tracking/reporting purposes. For example, the consumer might desire to inform the provider that surgery was performed on the left arm (which was broken), not the right arm. |
No resources found
No resources found
Note: links and images are rebased to the (stated) source
Manage the PHR Account Holder's history of surgical procedures.
The list of past procedures is a useful summary of what has been done in the past and anatomic changes have occurred that might influence current assessments and treatments. It is important to capture any surgical implants and associated lot/serial numbers for tracking/reporting purposes. For example, the consumer might desire to inform the provider that surgery was performed on the left arm (which was broken), not the right arm.
| PH.2.5.7#01 | dependent SHALL |
The system SHALL provide the ability to manage the surgical history including the presence or absence of elements and associated annotations that may exist in the provider(s) EHR or other systems, according to organizational policy and/or jurisdictional law. |
| PH.2.5.7#02 | MAY |
The system MAY provide the ability to capture, maintain, and transmit a request-for-correction to surgical history that was captured from an external source. Note: There could be multiple types of errors, both unintentional and intentional; the errors could also reside in multiple storage locations (primary, secondary, and intermediary); the errors could also reside in current records or in archived records; there could also be multiple sources (author, custodian-of-record, transcriptionist). |
| PH.2.5.7#03 | SHOULD |
The system SHOULD provide the PHR Account Holder with the ability to annotate the surgical history with text comments. |
| PH.2.5.7#04 | SHOULD |
The system SHOULD provide the ability to enter missing information regarding the surgical history list. |
| PH.2.5.7#05 | MAY |
The system MAY provide the ability to manage implant information (e.g., by collecting device-identification numbers for a hip, lens, or breast implant; or by capturing the date of the implant). |
| PH.2.5.7#06 | MAY |
The system MAY provide the ability to tag surgical history information (e.g., by category type (such as “implant”) or by procedure type (such as "excision" or "biopsy")). |
FHIR{
"resourceType" : "Requirements",
"id" : "PHRSFMR2-PH.2.5.7",
"meta" : {
"profile" : [
"http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/FMFunction"
]
},
"text" : {
"status" : "extensions",
"div" : "<div xmlns=\"http://www.w3.org/1999/xhtml\">\n <span id=\"description\"><b>Statement <a href=\"https://hl7.org/fhir/versions.html#std-process\" title=\"Normative Content\" class=\"normative-flag\">N</a>:</b> <div><p>Manage the PHR Account Holder's history of surgical procedures.</p>\n</div></span>\n\n \n <span id=\"purpose\"><b>Description <a href=\"https://hl7.org/fhir/versions.html#std-process\" title=\"Informative Content\" class=\"informative-flag\">I</a>:</b> <div><p>The list of past procedures is a useful summary of what has been done in the past and anatomic changes have occurred that might influence current assessments and treatments. It is important to capture any surgical implants and associated lot/serial numbers for tracking/reporting purposes. For example, the consumer might desire to inform the provider that surgery was performed on the left arm (which was broken), not the right arm.</p>\n</div></span>\n \n\n \n <span id=\"actors\"><b>Actors:</b><br/> ehr</span>\n \n\n \n <span id=\"requirements\"><b>Criteria <a href=\"https://hl7.org/fhir/versions.html#std-process\" title=\"Normative Content\" class=\"normative-flag\">N</a>:</b></span>\n \n <table id=\"statements\" class=\"grid dict\">\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>PH.2.5.7#01</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n <i>dependent</i>\n \n \n \n <span>SHALL</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHALL provide the ability to manage the surgical history including the presence or absence of elements and associated annotations that may exist in the provider(s) EHR or other systems, according to organizational policy and/or jurisdictional law.</p>\n</div></span>\n \n \n Satisfied by:<ol>\n \n <li><a href=\"https://www.hl7.org/fhir/procedure.html\">https://www.hl7.org/fhir/procedure.html</a></li>\n \n </ol>\n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>PH.2.5.7#02</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>MAY</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system MAY provide the ability to capture, maintain, and transmit a request-for-correction to surgical history that was captured from an external source. Note: There could be multiple types of errors, both unintentional and intentional; the errors could also reside in multiple storage locations (primary, secondary, and intermediary); the errors could also reside in current records or in archived records; there could also be multiple sources (author, custodian-of-record, transcriptionist).</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>PH.2.5.7#03</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHOULD provide the PHR Account Holder with the ability to annotate the surgical history with text comments.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>PH.2.5.7#04</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHOULD provide the ability to enter missing information regarding the surgical history list.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>PH.2.5.7#05</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>MAY</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system MAY provide the ability to manage implant information (e.g., by collecting device-identification numbers for a hip, lens, or breast implant; or by capturing the date of the implant).</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>PH.2.5.7#06</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>MAY</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system MAY provide the ability to tag surgical history information (e.g., by category type (such as “implant”) or by procedure type (such as "excision" or "biopsy")).</p>\n</div></span>\n \n \n </td>\n </tr>\n \n </table>\n</div>"
},
"extension" : [
{
"url" : "http://hl7.org/fhir/StructureDefinition/structuredefinition-wg",
"valueCode" : "ehr"
}
],
"url" : "http://hl7.org/ehrs/uv/phrsfmr2/Requirements/PHRSFMR2-PH.2.5.7",
"version" : "2.0.1-ballot",
"name" : "PH_2_5_7_Manage_Surgical_History",
"title" : "PH.2.5.7 Manage Surgical History (Function)",
"status" : "active",
"date" : "2025-04-03T15:15:30+00:00",
"publisher" : "EHR WG",
"contact" : [
{
"telecom" : [
{
"system" : "url",
"value" : "http://www.hl7.org/Special/committees/ehr"
}
]
}
],
"description" : "Manage the PHR Account Holder's history of surgical procedures.",
"purpose" : "The list of past procedures is a useful summary of what has been done in the past and anatomic changes have occurred that might influence current assessments and treatments. It is important to capture any surgical implants and associated lot/serial numbers for tracking/reporting purposes. For example, the consumer might desire to inform the provider that surgery was performed on the left arm (which was broken), not the right arm.",
"statement" : [
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent",
"valueBoolean" : true
}
],
"key" : "PHRSFMR2-PH.2.5.7-01",
"label" : "PH.2.5.7#01",
"conformance" : [
"SHALL"
],
"conditionality" : false,
"requirement" : "The system SHALL provide the ability to manage the surgical history including the presence or absence of elements and associated annotations that may exist in the provider(s) EHR or other systems, according to organizational policy and/or jurisdictional law.",
"satisfiedBy" : [
"https://www.hl7.org/fhir/procedure.html"
]
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "PHRSFMR2-PH.2.5.7-02",
"label" : "PH.2.5.7#02",
"conformance" : [
"MAY"
],
"conditionality" : false,
"requirement" : "The system MAY provide the ability to capture, maintain, and transmit a request-for-correction to surgical history that was captured from an external source. Note: There could be multiple types of errors, both unintentional and intentional; the errors could also reside in multiple storage locations (primary, secondary, and intermediary); the errors could also reside in current records or in archived records; there could also be multiple sources (author, custodian-of-record, transcriptionist)."
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "PHRSFMR2-PH.2.5.7-03",
"label" : "PH.2.5.7#03",
"conformance" : [
"SHOULD"
],
"conditionality" : false,
"requirement" : "The system SHOULD provide the PHR Account Holder with the ability to annotate the surgical history with text comments."
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "PHRSFMR2-PH.2.5.7-04",
"label" : "PH.2.5.7#04",
"conformance" : [
"SHOULD"
],
"conditionality" : false,
"requirement" : "The system SHOULD provide the ability to enter missing information regarding the surgical history list."
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "PHRSFMR2-PH.2.5.7-05",
"label" : "PH.2.5.7#05",
"conformance" : [
"MAY"
],
"conditionality" : false,
"requirement" : "The system MAY provide the ability to manage implant information (e.g., by collecting device-identification numbers for a hip, lens, or breast implant; or by capturing the date of the implant)."
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "PHRSFMR2-PH.2.5.7-06",
"label" : "PH.2.5.7#06",
"conformance" : [
"MAY"
],
"conditionality" : false,
"requirement" : "The system MAY provide the ability to tag surgical history information (e.g., by category type (such as “implant”) or by procedure type (such as \"excision\" or \"biopsy\"))."
}
]
}
XIG built as of ??metadata-date??. Found ??metadata-resources?? resources in ??metadata-packages?? packages.